`optimize()` was branching on whether the user passed a single minimizer
or an array, both for the gate ("does anything accept this asset?") and
for per-asset slicing. Normalize implementations and options to parallel
arrays once at the top of `optimize()` and reuse a single
`matchingMinimizers(name, info)` helper for both checks. Pass arrays to
`minify.js` unconditionally — it already normalizes a single function to
a one-element array internally.

Also extract the four extension regexes (JS/JSON/HTML/CSS) into shared
constants in `src/utils.js` so the 15 built-in `filter` helpers don't
each repeat the same literal.

The per-asset shallow clone in `optimize()` only existed because
`minify.js` mutated `module`/`ecma` on the caller's options object, which
would have leaked across assets when a single options object was shared.
Move that overlay inside the `minify.js` loop and build it as a fresh
object via spread, so the same source options reference is safe to reuse.

`optimize()` no longer pre-expands a `minimizerOptionsList`: when the
configured options are an array, slice the matching subset (references,
not clones); otherwise pass the single object straight through. With a
shared options object and N minimizers across M assets that drops the
cloning from N×M to a single overlay per minimizer call.

`Array.prototype.flat` only landed in Node 11; the engines field is
`>= 10.13.0`. Restore the `.filter` + `.map` split and stash each
asset's matched-minimizer indices in a `Map` keyed by name, so the
matching regexes still run only once per asset and the array of
records is built without `flat`.

terser 5.47.1 was published after the previous lockfile update; the CI
test matrix on Node 10/12/14/16/18 uses `npm install` (which re-resolves
to the latest within `^5.31.1`) so it pulled 5.47.1, while Node 20+
ran `npm ci` and stayed on 5.46.2. The two terser versions mangle the
same input to slightly different identifiers, which left the committed
snapshots only valid for one half of the matrix.

Run `npm update terser` to align the lockfile with what the older-Node
install path resolves to, then `jest -u` to refresh the affected
snapshots in TerserPlugin/test-option/extractComments-option suites.

Drop the standalone `test/minimizer-filter.test.js` and re-express the
same coverage as snapshot tests in `test/minify-option.test.js`,
matching the surrounding style (real fixtures, `readsAssets` /
`getErrors` / `getWarnings` snapshots). The four new cases cover:

- a single TerserPlugin instance dispatching to terser + html-minifier
  via the array-of-minimizers form
- a single minimizer whose `filter` returns false (asset stays as-is)
- a single minimizer whose `filter` returns undefined (treated as accept)
- an array of minimizers whose filters all reject the asset